User interaction processing in an electronic mail system

ABSTRACT

An e-mail system identifies actions or activities that a user takes relative to an e-mail message. The activity is logged as an activity log entry in an activity log. When the user accesses the activity log, the activities and corresponding e-mail messages are accessible to the user through the activity log entry, along with a user interface element that allows the user to take additional actions with respect to the e-mail message in the activity log entry.

CROSS-REFERENCE TO RELATED APPLICATION

The present application is a continuation of and claims priority of U.S.patent application Ser. No. 15/333,558, filed Oct. 25, 2016, the contentof which is hereby incorporated by reference in its entirety.

BACKGROUND

Computer systems are currently in wide use. Some such computer systemsare used to run electronic mail (e-mail) systems.

Some e-mail systems are hosted in a remote server environment (such asin the cloud or another environment) and are accessed by users who areusing client devices. The client devices may be mobile devices, desktopor laptop computers, etc. Some such e-mail systems are web-based e-mailsystems. This means that the users are accessing the hosted e-mailsystems through a web browser that runs on the client device orelsewhere.

To do so, the user often launches a web browser and then navigates to asite where the e-mail system (or service) is hosted, to perform e-mailoperations. The user can perform operations such as authoring an e-mailmessage, sending an e-mail message, reading an e-mail message, deletingor archiving an e-mail message, arranging folders, moving an e-mailmessage to a particular folder, setting filters, flagging an e-mailmessage, replying to an e-mail message, among a wide variety of otherthings.

The discussion above is merely provided for general backgroundinformation and is not intended to be used as an aid in determining thescope of the claimed subject matter.

SUMMARY

An e-mail system identifies actions or activities that a user takesrelative to an e-mail message. The activity is logged as an activity logentry in an activity log. When the user accesses the activity log, theactivities and corresponding e-mail messages are accessible to the userthrough the activity log entry, along with a user interface element thatallows the user to take additional actions with respect to the e-mailmessage in the activity log entry.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter. The claimed subject matter is not limited to implementationsthat solve any or all disadvantages noted in the background.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of one example of a computing systemarchitecture.

FIG. 2 is a block diagram showing one example of interaction processinglogic in more detail.

FIGS. 3-5 show examples of user interface displays.

FIG. 6 is a flow diagram illustrating one example of the operation ofthe architecture shown in FIG. 1 in generating an activity log entry.

FIG. 7 is a flow diagram illustrating one example of the operation ofthe architecture shown in FIG. 1 in surfacing an activity page for userinteraction.

FIG. 8 is a block diagram showing one example of the architectureillustrated in FIG. 1, deployed in a cloud computing architecture.

FIGS. 9-11 show examples of mobile devices that can be used in thearchitectures shown in the previous figures.

FIG. 12 is a block diagram showing one example of a computingenvironment that can be used in the architectures shown in the previousfigures.

DETAILED DESCRIPTION

Email systems can be systems that use mobile native email clientsystems, desktop email client systems and/or they can be web-basedsystems. Web-based systems allow a user to navigate to a site hostingthe e-mail system through a web browser, and perform e-mail activitiesor actions or functions within the e-mail system, through the webbrowser. It is not uncommon in any of these types of systems for a userto wish to view recent activities that he or she has taken in the e-mailsystem. For instance, it may be that a user is going through his or herinbox and deleting unwanted messages. It may be that the user hasdeleted, for instance, 10 messages, but now the user wishes to go backand review one of the previously deleted messages. In a web-based orother system, the user is often unable to do this in an effective way.The present discussion proceeds in the context of the email system beinga web-based system. However, it can just as easily apply to a desktopemail client and/or a mobile native email client. These are allcontemplated herein.

The user can use backstacking functionality in the web browser to reachthe previous state in the browser, and thus to reach the previous e-mailthat the user was just interacting with. However, backstacking posessignificant limitations. For instance, if the user opens a new browserwidow, he or she loses the backstacking history. In addition,backstacking does not keep track of which types of actions have beentaken with respect to the email message that the user previouslyinteracted with. For instance, the backstacking history may provide noindication as to whether the user flagged the e-mail message, deletedit, replied to it, etc.

In addition, if a user wishes to undo any of his or her previousactions, the user cannot do this through backstacking. By way ofexample, assuming that the user has deleted 10 e-mails in a row, and theuser now wishes to undo deletion of the third e-mail message, this isnot currently possible by using backstacking functionality.

The present discussion thus proceeds with respect to describing anactivity log generation system that maintains an activity log thatidentifies particular e-mail messages, and user actions or activitiesthat were taken with respect to those messages. The system can alsoprovide user actuable elements that can be used to interact with entriesin the activity log, such as to undo the actions or activities relativeto a given e-mail message, among other things.

FIG. 1 is a block diagram of one example of a computing systemarchitecture 100. Architecture 100 includes computing system 102 thatcan be accessed by client computing system 104 over network 106. FIG. 1also shows that client computing system 104 can generate or present oneor more user interfaces 108 with user input mechanisms 110, forinteraction by user 112. User 112 illustratively interacts with the userinput mechanisms 110 to control and manipulate client computing system104 and computing system 102.

In the example illustrated in FIG. 1, client computing system 104illustratively includes one or more servers or processors 114, webbrowser 116, data store 118, user interface logic 120, and it caninclude a wide variety of other functionality 122. User 112 can interactwith user input mechanisms 110 in order to launch and use web browser116 that is run by client computing system 104.

In the example shown in FIG. 1, computing system 102 illustrativelyincludes one or more processors or servers 124, electronic mail (e-mail)system 126, data store 128 (which can include activity log 152 and otheritems 154), user interface logic 130, and it can include a wide varietyof other functionality or other items 132. E-mail system 126illustratively includes e-mail functionality 134 that allows user 112,once he or she has navigated to e-mail system 126 using web browser 116,to perform a wide variety of e-mail functions. Such functions caninclude authoring, sending, and replying to electronic mail messages,deleting messages, arranging folders, flagging messages, settingfilters, and a wide variety of other functions.

E-mail system 126 also illustratively includes activity log generationsystem 136. It will be noted that an example in which system 136 andactivity log 152 are located on the server side is only one example, andsystem 126 and/or log 152 can be client side items as well. When locatedon client computing system 104, then they may only be available for thatclient (or user session). This is contemplated herein. However, theremaining discussion will be in the context of system 136 and log 152being server side items. The discussion can just as easily apply to thembeing client side as well, and this is contemplated herein.

System 136, itself, illustratively includes activity identifier logic138, item identifier logic 140, logging logic 142, activity loginvocation logic 144, activity log page generator logic 146, interactionprocessing logic 148, and it can include other items 150. Activityidentifier logic 138 illustratively identifies any activities or actionsthat user 112 takes with respect to any e-mail messages in e-mail system126. Item identifier logic 140 identifies the particular e-mail messagecorresponding to that activity or action, and logging logic 142generates an activity log entry in activity log 152 in data store 128.The activity log entry identifies the email message, the user activityor action taken relative to that email message, and it can also includea user actuatable element or other items.

Activity log invocation logic 144 illustratively detects when user 112has indicated that he or she wishes to view or interact with theactivity log 152. Activity log page generator logic 146 then generatesan activity log page indicative of the entries in the activity log 152,and surfaces that page (such as through user interface logic 130 and webbrowser 116) for review and interaction by user 112. Interactionprocessing logic 148 illustratively detects user interaction with useractuatable elements on the activity log page, and performs processingbased upon the detected user interaction. These are all described ingreater detail below.

FIG. 2 is a block diagram showing one example of interaction processinglogic 148, in more detail. In the example shown in FIG. 2, logic 148illustratively includes interaction detector 160, undo logic 162, andother interaction processing logic 164. Recall that interactionprocessing logic 148 illustratively detects user interactions with theactivity log page after the user has requested that the activity logpage be surfaced. The interactions can be any of a wide variety ofdifferent interactions, such as an interaction undoing apreviously-performed user activity, an interaction to display a fullemail message represented by a log entry, or other interaction. Thus,interaction detector 160 illustratively detects user interaction with anentry in the activity log on the activity log page. This can be done bydetecting user interaction with a user (UI) interface element (UI) thatis provided by activity log page generator logic 146, and that allowsthe user to take an action with respect to a log entry.

In one example, the UI element is an undo UI element that can beactuated by the user to undo the action or activity reflected in theactivity log entry. Thus, in one example, undo logic 162 can includeflag undo logic 166, delete undo logic 168, archive undo logic 170, moveundo logic 172, and other logic 174.

Flag undo logic 166 undoes a flagging operation. For instance, where theuser has flagged an e-mail message, flag undo logic 166 is actuated tounflag that message.

Delete undo logic 168 undoes a delete action. For instance, where theuser has deleted an e-mail message, delete undo logic 168 undoes thedeletion operation and places the message back in the user's inbox (orwhatever other portion of the e-mail system it resided in prior to beingdeleted).

Archive undo logic 170 undoes an archive operation. For instance, wherea user has archived an e-mail message, archive undo logic removes thatmessage from the archive and places it in the state it was in prior tothe user performing the archive activity or action.

Move undo logic 172 undoes a move action or activity. Thus, where theuser had moved an e-mail message, such as from one folder to anotherfolder, move undo logic 172 will undo that operation and place themessage back in the location where it resided prior to the move actionor activity.

Of course, it will be appreciated that these are only examples ofactions that can be undone. In addition, the undo functionality is onlyone example of a function for which a user interface element can beprovided to the user on the activity log page. User interface elementscan be provided to allow the user to perform other actions relative toentries in the activity log as well.

Before describing the operation of the architecture shown in FIGS. 1 and2 in more detail, a number of user interface displays will first bedescribed, for the sake of example. FIGS. 3-5 show examples of userinterface displays that can be generated by architecture 100. Again,these are examples only and a wide variety of other user interfaces canbe generated as well.

FIG. 3 shows one example of a user interface display 180 that can begenerated by electronic mail system 126 and surfaced for user 112through web browser 116. In the example shown in FIG. 3, user interfacedisplay 180 illustratively includes a folders pane 182, a messages pane184, and a reading pane 186. Folders pane 182 illustratively displaysthe various folders that user 112 has set up, or that are automaticallyset up, in e-mail system 126. It can be seen in FIG. 3 that the “inbox”folder 188 has been selected.

Messages pane 184 displays a set of messages that are in the highlightedfolder in pane 182. Therefore, in the example shown in FIG. 3, messagespane 184 shows a plurality of different messages 190-192 that reside inthe user's inbox folder 188. The messages 190 and 192 are identified inmessages pane 184 by message information that corresponds to a subset ofthe actual messages. Therefore, for example, messages 190 and 192include the sender information, the regarding information, and they caninclude an excerpt or another portion of the actual message body. Theseare examples only.

Reading pane 186 illustratively displays the message content for amessage selected in messages pane 184. The reading pane can thus displaya message header 194, message body 196, thread information 198 or otherinformation. Message header 194 illustratively includes headerinformation for the message, such as the sender, the date and time itwas sent, the regarding information, etc. Message body 196illustratively includes message body information, and thread information198 shows thread history, and other information regarding the message(such as messages it was in reply to, etc.).

When the user takes action or performs an activity with respect to amessage, activity logic generation system 136 (as will be described ingreater detail below with respect to FIGS. 6 and 7) illustrativelydetects that action or activity and correlates it to the message forwhich the action or activity was taken. It generates an activity logentry and stores that entry in the activity log 152 in the data store128 shown in FIG. 1.

In the example shown in FIG. 3, user interface display 180 alsoillustratively includes an activity log actuator 200. Actuator 200 isillustratively a user actuatable element that can be actuated by theuser in order to invoke system 136 to display an activity log pageshowing the log entries in activity log 152 (or to otherwise let theuser access the activity log 152).

FIG. 4 illustrates another example of user interface display 180. Someof the items shown in FIG. 4 are similar to those shown in FIG. 3, andthey are similarly numbered. FIG. 4 shows that, because the user hasactuated the activity log actuator 200, activity log page generatorlogic 146 has generated an activity log page or display and displayed itin activity log pane 202. In one example, activity log pane 202 displaysemail message identifiers corresponding to e-mails that have been actedon by user 112, and the actions that the user took, and possibly otheritems (as will be described in more detail below) in reversechronological order. Therefore, the e-mail messages that have been actedon most recently are displayed on the top of activity log pane 202,while the e-mail messages that have been acted on later are displayedlower down on pane 202.

Each e-mail message, and the corresponding action, are illustrativelyrepresented by a log entry in activity log 152. Thus, a first log entrydisplayed on activity log pane 202 includes e-mail messageidentifier/excerpt 204, action identifier 206, one or more UI elements208, and it can include other items 210. The next entry in activity log152 includes e-mail message identifier/excerpt 212, action identifier214, one or more UI elements 216, and it can include other items 218.

While only two activity log entries are shown in activity log pane 202,it will be appreciated that a larger number can be displayed as well.For instance, it may be that the activity log pane 202 displays the mostrecent 10 or 20 or 100 activity log entries. Where the number of logentries that are displayed in activity log pane 202 is too large to bedisplayed, pane 202 may be scrollable, using a suitable user inputmechanism, such as the scroll bar 220 shown in FIG. 4.

E-mail message identifier/excerpt 204 may provide identifyinginformation which identifies the e-mail message that is the subject ofthe activity log entry. For instance, it may be similar to theinformation displayed for message 190 in message pane 184. It may bedifferent as well. However, in one example, it indicates the author ofthe message, what the message is regarding, and may include an excerptof the message body. This is just one example and more, less ordifferent information may be included in the e-mail messageidentifier/excerpt 204.

Action identifier 206 illustratively identifies to user 112 the actionor activity that he or she took relative to the identified e-mailmessage. Action identifier 206 may be a natural language text stringsuch as “this message was deleted” and it may identify the date and timethat the action was taken. In other examples, it may identify the actionin other ways as well.

UI element 208 is illustratively a user actuatable element that can beactuated by user 112 in order to take an action with respect to thecorresponding activity log entry. For instance, where the actionidentified by action identifier 206 can be undone, then UI element 208may be an undo actuator which can be actuated by the user 112 to undothat action with respect to the corresponding message. The UI element208 may be another user actuatable element to perform other actions aswell. The undo action is given by way of example only.

In the example discussed above, it can be seen that each activity logentry illustratively has an e-mail identifier that identifies the e-mailand an action identifier that identifies the corresponding action. Theentry may also have a UI element that allows the user to perform sometype of action with respect to the action or activity identified in theactivity log entry. However, where the action cannot be undone, or wherethe user would not be permitted to perform any other type of action withrespect to that activity log entry, there may be no UI element in thedisplayed activity log entry, or it may be greyed out indicating that itis not active, or it may be displayed in other ways as well.

In another example, the user may be able to view the full e-mail messageidentified by the e-mail message identifier/excerpt in the activity logentry. For instance, it may be that the user wishes to view the entiree-mail message identified by e-mail message identifier/excerpt 212 inthe second activity log entry displayed in activity log pane 202. Inthat case, the user may double click the e-mail messageidentifier/excerpt 212, or otherwise select or actuate that entry. Inresponse, interaction processing logic 148 may illustratively retrievethe entire e-mail message from the activity log 152, and display it tothe user. FIG. 5 shows one example of this.

FIG. 5 is another example of user interface display 180. Some of theitems are similar to those shown in FIG. 4, and they are similarlynumbered. However, it can now be seen that the user has actuated thee-mail message identifier/excerpt 212 for the second activity log entryin the activity log pane 202. In response, e-mail message retrieval andsurfacing logic 163 illustratively retrieves the corresponding e-mailmessage and generates a display to surface the content of that e-mailmessage for user 112, through browser 116. Thus FIG. 5 shows that theemail message display 230 has now been generated on user interfacedisplay 180. The e-mail message display 230 includes a message headerportion 232 for the e-mail message identified by e-mail messageidentifier/excerpt 212. It includes message body portion 234, threadinformation portion 236, and it can also include an action identifier238 that identifies the action that was taken on the e-mail (which maybe the same as action identifier 214 or different). It can also includeone or more UI elements 240 which allow user 112 to perform anotheraction or activity with respect to the e-mail message represented indisplay 230. This may be the same UI element as UI element 216 shown inactivity log pane 204, or it may be different.

The operation of architecture 100 will now be described in more detail.FIG. 6 is a flow diagram illustrating one example of the operation ofarchitecture 100 (shown in FIG. 1) in generating an activity log entryand storing it in activity log 152 in data store 128. It is firstassumed in FIG. 6 that web browser 116 is open and that the user hasnavigated to the site that is hosting the user's e-mail system 126. Thisis indicated by block 242 in the flow diagram of FIG. 6. A userinterface display, such as that shown in FIG. 3, may be generated forthe user, when the user has navigated to the user's e-mail system. Ofcourse, this is only one example of a display that may be generated andmany other or different displays can be generated as well.

E-mail functionality 134 then detects that the user has selected ane-mail message from the user interface display. For instance, it may bethat the user has actuated the message display 190 in the message pane184 in FIG. 3 to indicate that the user wishes to read, reply to, orotherwise take action with respect to the corresponding e-mail message.Detecting user selection of an e-mail message is indicated by block 244in the flow diagram of FIG. 6.

Activity identifier logic 138 then detects a user activity (or action)that the user takes relative to the selected message. This is indicatedby block 246, and it can be done in a variety of different ways. Forinstance, in one example, it detects user interaction with a UI element(such as on user interface display 180). This is indicated by block 248.It can also receive notification from other e-mail functionality 134that the user has taken some type of action relative to the selectede-mail message. This is indicated by block 250. It can detect the useractivity or action relative to the selected message in a wide variety ofother ways as well, and this is indicated by block 252.

The activities or actions can be any of a wide variety of differenttypes of activities or actions. For instance, it may be that the userflags the e-mail as indicated by block 254. The user may also reply tothe message as indicated by block 256. The user may delete or archivethe message as indicated by block 258 and 260, respectively. The usermay move the message or author and send a message as indicated by blocks262 and 264, respectively. Of course, the user can perform an activityor action with respect to the selected message in a wide variety ofother ways, and this is indicated by block 266.

Logging logic 142 then receives the activity identifier identified byactivity identifier logic 138 and the corresponding e-mail identified byitem identifier logic 140 and generates an activity log entry and storesit in activity log 152 for user 112. Generating the activity log entryfor the detected user activity is indicated by block 268. The activitylog entry can include a variety of different information. As discussedabove with respect to FIGS. 4 and 5, it may include an e-mail messageidentifier portion 270, an action identifier portion 272, a UI elementidentifier portion 274, and it can include other items 276.

Once it is generated, logging logic 142 stores the activity log entryfor the detected user activity in an activity log 152 for the user 112.This is indicated by block 278. In one example, where an activity log152 already exists for this user, logic 142 adds the activity log entryto the activity log 152 as the most recent entry. Where an activity loghas not yet been created for this user, logic 142 creates an activitylog and adds the entry to the newly created activity log.

FIG. 7 is a flow diagram illustrating one example of the operation ofarchitecture 100 in allowing user 112 to invoke the activity logprocessing (so the user can view an activity log page) and in processingany user interactions with the activity log page. Activity loginvocation logic 144 first detects user invocation of the activity logand generates an invocation signal indicative of this detectedinvocation. This is indicated by block 290 in the flow diagram of FIG.7. In one example, the user actuates a user actuatable UI element, suchas actuator 200 shown in FIG. 4. Actuation of a UI element is indicatedby block 292 in the flow diagram of FIG. 7. In another example, the usercan invoke the activity log processing using a touch gesture 294, aspeech input 296, or using any of a wide variety of other inputs 298.

Activity log page generator logic 146 then accesses the activity log 152for user 112 to generate an activity log page. This is indicated byblock 300. In one example, the number of activity log entries providedto the user on the activity log page is limited to the N most recentactivity log entries, where N can be pre-defined or can changedynamically. In another example, the number of log entries is limited tothose that were just created during the present browser session. In yetanother example, the number of log entries generated on the activity logpage can be a large or unlimited number, with the most recent X entriesdisplayed on the activity log page, but with the other log entriesaccessible by scrolling or otherwise manipulating the activity log page.In another example, the activity log entries that are displayed on theactivity log page can be those created across multiple different browsersessions, or in other ways.

Activity log page generator logic 146 then generates a control signal tocontrol user interface logic 130 to surface the activity log page foruser 112, through web browser 116. Surfacing the activity log page foruser review or interaction is indicated by block 302 in the flow diagramof FIG. 7. The activity log page can include entries identifying thee-mail messages with the e-mail message identifier as indicated by block304. They can include the action identifiers as indicated by block 306.They can include user actuatable UI elements as indicated by block 308,or the entries can include a wide variety of other items as indicated byblock 310.

User interaction processing logic 148 then detects any user interactionswith the activity log page (or with any individual entries in theactivity log page). This is indicated by block 312. For instance,interaction detector 160 can detect that the user has scrolled theactivity log page to view additional entries. This is indicated by block314. It can detect that the user has selected an e-mail messagecorresponding to one of the activity log entries, such as by doubleclicking on an e-mail message identifier/excerpt as described above.Selecting a message in this way is indicated by block 316. It can detectthat the user has actuated one of the UI elements, such as an undo UIelement, as indicated by block 318. It can detect user interactions in avariety of other ways as well, and this is indicated by block 320.

Interaction processing logic 148 then generates control signals toprogrammatically control email functionality 134 in email system 126 toperform processing corresponding to the detected user interaction. Thisis indicated by block 322. For instance, where the user has selected amessage for display, e-mail message retrieval and surfacing logic 163illustratively controls email system 126 to retrieve the full e-mailmessage content and display the selected message for the user (such asshown in FIG. 5 above). In one example, it can display the message inedit mode so that the user can edit the message, or it can display themessage in other modes as well. Displaying the selected message isindicated by block 324 in the flow diagram of FIG. 7.

In another example, undo logic 162 can generate control signals toprogrammatically control email functionality 134 in email system 126 toundo the identified action, based upon the detected user interactionwith one of the UI elements. This is indicated by block 326. By way ofexample, if the action was to flag the e-mail message, and the useractuated the undo actuator, then flag undo logic 166 can generatecontrol signals to control email system 126 to un-flag the message. Ifthe action was to delete the message, then delete undo logic 168 cangenerate control signals to control email system 126 to reverse thataction. If the action was to archive or move the message, then archiveundo logic 170 or move undo logic 172 can generate control signals tocontrol email system 126 to undo those actions as well.

In generating control signals to control email system 126, it may bethat the email functionality 134 exposes one or more applicationprogramming interfaces (APIs) that can be called by logic 148 to performthe desired action. The control signals can be generated and used inother ways as well.

It will be appreciated that the interaction processing can take otherforms as well. This is indicated by block 328.

It can thus be seen that the present discussion addresses difficultiesassociated with maintaining and surfacing an e-mail activity log througha web-based e-mail system. The present discussion overcomes thedifficulties associated with using backstacking in a web browser 116 inorder to accomplish this. It also improves the accuracy, usability, andflexibility of the system. Because the activity log is detected andgenerated by the e-mail system itself, or by a service separate from butaccessed by the e-mail system, changes to web browser 116 do not affectusage or maintenance of the activity log. Similarly, if changes are madeto the activity log, so long as they are accessible by web browser 116,those changes will be incorporated and surfaced for the user. All ofthis increases the flexibility in the design and development of thesystem, and it greatly enhances the usability of the system for theuser. It also adds features previously unavailable in web-based systems.

It will be noted that the above discussion has described a variety ofdifferent systems, components and/or logic. It will be appreciated thatsuch systems, components and/or logic can be comprised of hardware items(such as processors and associated memory, or other processingcomponents, some of which are described below) that perform thefunctions associated with those systems, components and/or logic. Inaddition, the systems, components and/or logic can be comprised ofsoftware that is loaded into a memory and is subsequently executed by aprocessor or server, or other computing component, as described below.The systems, components and/or logic can also be comprised of differentcombinations of hardware, software, firmware, etc., some examples ofwhich are described below. These are only some examples of differentstructures that can be used to form the systems, components and/or logicdescribed above. Other structures can be used as well.

The present discussion has mentioned processors and servers. In oneembodiment, the processors and servers include computer processors withassociated memory and timing circuitry, not separately shown. They arefunctional parts of the systems or devices to which they belong and areactivated by, and facilitate the functionality of the other componentsor items in those systems.

Also, a number of user interface displays have been discussed. They cantake a wide variety of different forms and can have a wide variety ofdifferent user actuatable input mechanisms disposed thereon. Forinstance, the user actuatable input mechanisms can be text boxes, checkboxes, icons, links, drop-down menus, search boxes, etc. They can alsobe actuated in a wide variety of different ways. For instance, they canbe actuated using a point and click device (such as a track ball ormouse). They can be actuated using hardware buttons, switches, ajoystick or keyboard, thumb switches or thumb pads, etc. They can alsobe actuated using a virtual keyboard or other virtual actuators. Inaddition, where the screen on which they are displayed is a touchsensitive screen, they can be actuated using touch gestures. Also, wherethe device that displays them has speech recognition components, theycan be actuated using speech commands.

A number of data stores have also been discussed. It will be noted theycan each be broken into multiple data stores. All can be local to thesystems accessing them, all can be remote, or some can be local whileothers are remote. All of these configurations are contemplated herein.

Also, the figures show a number of blocks with functionality ascribed toeach block. It will be noted that fewer blocks can be used so thefunctionality is performed by fewer components. Also, more blocks can beused with the functionality distributed among more components.

FIG. 8 is a block diagram of architecture 100, shown in FIG. 1, exceptthat its elements are disposed in a cloud computing architecture 500.Cloud computing provides computation, software, data access, and storageservices that do not require end-user knowledge of the physical locationor configuration of the system that delivers the services. In variousembodiments, cloud computing delivers the services over a wide areanetwork, such as the internet, using appropriate protocols. Forinstance, cloud computing providers deliver applications over a widearea network and they can be accessed through a web browser or any othercomputing component. Software or components of architecture 100 as wellas the corresponding data, can be stored on servers at a remotelocation. The computing resources in a cloud computing environment canbe consolidated at a remote data center location or they can bedispersed. Cloud computing infrastructures can deliver services throughshared data centers, even though they appear as a single point of accessfor the user. Thus, the components and functions described herein can beprovided from a service provider at a remote location using a cloudcomputing architecture. Alternatively, they can be provided from aconventional server, or they can be installed on client devicesdirectly, or in other ways.

The description is intended to include both public cloud computing andprivate cloud computing. Cloud computing (both public and private)provides substantially seamless pooling of resources, as well as areduced need to manage and configure underlying hardware infrastructure.

A public cloud is managed by a vendor and typically supports multipleconsumers using the same infrastructure. Also, a public cloud, asopposed to a private cloud, can free up the end users from managing thehardware. A private cloud may be managed by the organization itself andthe infrastructure is typically not shared with other organizations. Theorganization still maintains the hardware to some extent, such asinstallations and repairs, etc.

In the example shown in FIG. 8, some items are similar to those shown inFIG. 1 and they are similarly numbered. FIG. 8 specifically shows thatcomputing system 102 can be located in cloud 502 (which can be public,private, or a combination where portions are public while others areprivate). Therefore, user 112 uses a user device 504 that includesclient computing system 104 to access those systems through cloud 502.

FIG. 8 also depicts another example of a cloud architecture. FIG. 8shows that it is also contemplated that some elements of computingsystem 102 can be disposed in cloud 502 while others are not. By way ofexample, data store 128 can be disposed outside of cloud 502, andaccessed through cloud 502. In another example, activity log generationsystem 136 can be outside of cloud 502. Regardless of where they arelocated, they can be accessed directly by device 504, through a network(either a wide area network or a local area network), they can be hostedat a remote site by a service, or they can be provided as a servicethrough a cloud or accessed by a connection service that resides in thecloud. All of these architectures are contemplated herein.

It will also be noted that architecture 100, or portions of it, can bedisposed on a wide variety of different devices. Some of those devicesinclude servers, desktop computers, laptop computers, tablet computers,or other mobile devices, such as palm top computers, cell phones, smartphones, multimedia players, personal digital assistants, etc.

FIG. 9 is a simplified block diagram of one illustrative example of ahandheld or mobile computing device that can be used as a user's orclient's hand held device 16, in which the present system (or parts ofit) can be deployed. FIGS. 10-11 are examples of handheld or mobiledevices.

FIG. 9 provides a general block diagram of the components of a clientdevice 16 that can run components of client computing system 104 or thatotherwise interacts with architecture 100, or both. In the device 16, acommunications link 13 is provided that allows the handheld device tocommunicate with other computing devices and under some embodimentsprovides a channel for receiving information automatically, such as byscanning. Examples of communications link 13 include an infrared port, aserial/USB port, a cable network port such as an Ethernet port, and awireless network port allowing communication though one or morecommunication protocols including General Packet Radio Service (GPRS),LTE, HSPA, HSPA+ and other 3G and 4G radio protocols, 1×rtt, and ShortMessage Service, which are wireless services used to provide cellularaccess to a network, as well as Wi-Fi protocols, and Bluetooth protocol,which provide local wireless connections to networks.

In other examples, applications or systems are received on a removableSecure Digital (SD) card that is connected to a SD card interface 15. SDcard interface 15 and communication links 13 communicate with aprocessor 17 (which can also embody processors or servers 114 fromFIG. 1) along a bus 19 that is also connected to memory 21 andinput/output (I/O) components 23, as well as clock 25 and locationsystem 27.

I/O components 23, in one embodiment, are provided to facilitate inputand output operations. I/O components 23 for various embodiments of thedevice 16 can include input components such as buttons, touch sensors,multi-touch sensors, optical or video sensors, voice sensors, touchscreens, proximity sensors, microphones, tilt sensors, and gravityswitches and output components such as a display device, a speaker, andor a printer port. Other I/O components 23 can be used as well.

Clock 25 illustratively comprises a real time clock component thatoutputs a time and date. It can also, illustratively, provide timingfunctions for processor 17.

Location system 27 illustratively includes a component that outputs acurrent geographical location of device 16. This can include, forinstance, a global positioning system (GPS) receiver, a LORAN system, adead reckoning system, a cellular triangulation system, or otherpositioning system. It can also include, for example, mapping softwareor navigation software that generates desired maps, navigation routesand other geographic functions.

Memory 21 stores operating system 29, network settings 31, applications33, application configuration settings 35, data store 37, communicationdrivers 39, and communication configuration settings 41. Memory 21 caninclude all types of tangible volatile and non-volatilecomputer-readable memory devices. It can also include computer storagemedia (described below). Memory 21 stores computer readable instructionsthat, when executed by processor 17, cause the processor to performcomputer-implemented steps or functions according to the instructions.Similarly, device 16 can have a client system 24 which can run variousbusiness applications or embody parts of computing system 102. Processor17 can be activated by other components to facilitate theirfunctionality as well.

Examples of the network settings 31 include things such as proxyinformation, Internet connection information, and mappings. Applicationconfiguration settings 35 include settings that tailor the applicationfor a specific enterprise or user. Communication configuration settings41 provide parameters for communicating with other computers and includeitems such as GPRS parameters, SMS parameters, connection user names andpasswords.

Applications 33 can be applications that have previously been stored onthe device 16 or applications that are installed during use, althoughthese can be part of operating system 29, or hosted external to device16, as well.

FIG. 10 shows one example in which device 16 is a tablet computer 600.In FIG. 10, computer 600 is shown with user interface display screen602. Screen 602 can be a touch screen (so touch gestures from a user'sfinger can be used to interact with the application) or a pen-enabledinterface that receives inputs from a pen or stylus. It can also use anon-screen virtual keyboard. Of course, it might also be attached to akeyboard or other user input device through a suitable attachmentmechanism, such as a wireless link or USB port, for instance. Computer600 can also illustratively receive voice inputs as well.

FIG. 11 shows that the device can be a smart phone 71. Smart phone 71has a touch sensitive display 73 that displays icons or tiles or otheruser input mechanisms 75. Mechanisms 75 can be used by a user to runapplications, make calls, perform data transfer operations, etc. Ingeneral, smart phone 71 is built on a mobile operating system and offersmore advanced computing capability and connectivity than a featurephone.

Note that other forms of the devices 16 are possible.

FIG. 12 is one example of a computing environment in which architecture100, or parts of it, (for example) can be deployed. With reference toFIG. 12, an example system for implementing some embodiments includes ageneral-purpose computing device in the form of a computer 810.Components of computer 810 may include, but are not limited to, aprocessing unit 820 (which can comprise processors or servers 114 or124), a system memory 830, and a system bus 821 that couples varioussystem components including the system memory to the processing unit820. The system bus 821 may be any of several types of bus structuresincluding a memory bus or memory controller, a peripheral bus, and alocal bus using any of a variety of bus architectures. By way ofexample, and not limitation, such architectures include IndustryStandard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus,Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA)local bus, and Peripheral Component Interconnect (PCI) bus also known asMezzanine bus. Memory and programs described with respect to FIG. 1 canbe deployed in corresponding portions of FIG. 12.

Computer 810 typically includes a variety of computer readable media.Computer readable media can be any available media that can be accessedby computer 810 and includes both volatile and nonvolatile media,removable and non-removable media. By way of example, and notlimitation, computer readable media may comprise computer storage mediaand communication media. Computer storage media is different from, anddoes not include, a modulated data signal or carrier wave. It includeshardware storage media including both volatile and nonvolatile,removable and non-removable media implemented in any method ortechnology for storage of information such as computer readableinstructions, data structures, program modules or other data. Computerstorage media includes, but is not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CD-ROM, digital versatile disks (DVD)or other optical disk storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othermedium which can be used to store the desired information and which canbe accessed by computer 810. Communication media typically embodiescomputer readable instructions, data structures, program modules orother data in a transport mechanism and includes any informationdelivery media. The term “modulated data signal” means a signal that hasone or more of its characteristics set or changed in such a manner as toencode information in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, RF,infrared and other wireless media. Combinations of any of the aboveshould also be included within the scope of computer readable media.

The system memory 830 includes computer storage media in the form ofvolatile and/or nonvolatile memory such as read only memory (ROM) 831and random access memory (RAM) 832. A basic input/output system 833(BIOS), containing the basic routines that help to transfer informationbetween elements within computer 810, such as during start-up, istypically stored in ROM 831. RAM 832 typically contains data and/orprogram modules that are immediately accessible to and/or presentlybeing operated on by processing unit 820. By way of example, and notlimitation, FIG. 12 illustrates operating system 834, applicationprograms 835, other program modules 836, and program data 837.

The computer 810 may also include other removable/non-removablevolatile/nonvolatile computer storage media. By way of example only,FIG. 12 illustrates a hard disk drive 841 that reads from or writes tonon-removable, nonvolatile magnetic media, and an optical disk drive 855that reads from or writes to a removable, nonvolatile optical disk 856such as a CD ROM or other optical media. Other removable/non-removable,volatile/nonvolatile computer storage media that can be used in theexemplary operating environment include, but are not limited to,magnetic tape cassettes, flash memory cards, digital versatile disks,digital video tape, solid state RAM, solid state ROM, and the like. Thehard disk drive 841 is typically connected to the system bus 821 througha non-removable memory interface such as interface 840, and optical diskdrive 855 are typically connected to the system bus 821 by a removablememory interface, such as interface 850.

Alternatively, or in addition, the functionality described herein can beperformed, at least in part, by one or more hardware logic components.For example, and without limitation, illustrative types of hardwarelogic components that can be used include Field-programmable Gate Arrays(FPGAs), Program-specific Integrated Circuits (ASICs), Program-specificStandard Products (ASSPs), System-on-a-chip systems (SOCs), ComplexProgrammable Logic Devices (CPLDs), etc.

The drives and their associated computer storage media discussed aboveand illustrated in FIG. 12, provide storage of computer readableinstructions, data structures, program modules and other data for thecomputer 810. In FIG. 12, for example, hard disk drive 841 isillustrated as storing operating system 844, application programs 845,other program modules 846, and program data 847. Note that thesecomponents can either be the same as or different from operating system834, application programs 835, other program modules 836, and programdata 837. Operating system 844, application programs 845, other programmodules 846, and program data 847 are given different numbers here toillustrate that, at a minimum, they are different copies.

A user may enter commands and information into the computer 810 throughinput devices such as a keyboard 862, a microphone 863, and a pointingdevice 861, such as a mouse, trackball or touch pad. Other input devices(not shown) may include a joystick, game pad, satellite dish, scanner,or the like. These and other input devices are often connected to theprocessing unit 820 through a user input interface 860 that is coupledto the system bus, but may be connected by other interface and busstructures, such as a parallel port, game port or a universal serial bus(USB). A visual display 891 or other type of display device is alsoconnected to the system bus 821 via an interface, such as a videointerface 890. In addition to the monitor, computers may also includeother peripheral output devices such as speakers 897 and printer 896,which may be connected through an output peripheral interface 895.

The computer 810 is operated in a networked environment using logicalconnections to one or more remote computers, such as a remote computer880. The remote computer 880 may be a personal computer, a hand-helddevice, a server, a router, a network PC, a peer device or other commonnetwork node, and typically includes many or all of the elementsdescribed above relative to the computer 810. The logical connectionsdepicted in FIG. 12 include a local area network (LAN) 871 and a widearea network (WAN) 873, but may also include other networks. Suchnetworking environments are commonplace in offices, enterprise-widecomputer networks, intranets and the Internet.

When used in a LAN networking environment, the computer 810 is connectedto the LAN 871 through a network interface or adapter 870. When used ina WAN networking environment, the computer 810 typically includes amodem 872 or other means for establishing communications over the WAN873, such as the Internet. The modem 872, which may be internal orexternal, may be connected to the system bus 821 via the user inputinterface 860, or other appropriate mechanism. In a networkedenvironment, program modules depicted relative to the computer 810, orportions thereof, may be stored in the remote memory storage device. Byway of example, and not limitation, FIG. 12 illustrates remoteapplication programs 885 as residing on remote computer 880. It will beappreciated that the network connections shown are exemplary and othermeans of establishing a communications link between the computers may beused.

It should also be noted that the different embodiments described hereincan be combined in different ways. That is, parts of one or moreembodiments can be combined with parts of one or more other embodiments.All of this is contemplated herein.

Example 1 is a computing system, comprising:

an electronic mail (email) system that is user accessible to perform aplurality of different types of activities relative to an email message;

an activity log generation system that generates an activity log thathas log entries, activity log generation system generating each logentry to identify an activity taken relative to a corresponding emailmessage and to identify the corresponding email message, the activitylog generation system generating a log entry in the activity log foreach of the plurality of different types of activities taken relative todifferent corresponding email messages, at least one log entry includinga user interface element that is user actuatable to perform an actionrelative to the log entry; and

user interface logic that generates a control signal to controlsurfacing of the activity log.

Example 2 is the computing system of any or all previous examples

wherein the email system is a web-based email system that is useraccessible through a web browser and wherein the activity log generationsystem comprises:

activity identifier logic configured to identify a detected useractivity taken relative to a given corresponding email message.

Example 3 is the computing system of any or all previous exampleswherein the activity log generation system comprises:

item identifier logic configured to identify the given correspondingemail message.

Example 4 is the computing system of any or all previous exampleswherein the activity log generation system comprises:

logging logic configured to generate a corresponding activity log entry,in the activity log, that identifies the detected user activityperformed relative to the given corresponding email message, theweb-based email system being configured to expose the activity logthrough the user interface logic and the web browser.

Example 5 is the computing system of any or all previous examples andfurther comprising:

activity log invocation logic configured to detect user invocation ofthe activity log, corresponding to the user, through the web browser,and generate an invocation signal indicative of the detected userinvocation.

Example 6 is the computing system of any or all previous exampleswherein the web-based email system generates an email user interfacedisplay with an activity log actuator that is actuatable to invoke theactivity log corresponding to the user.

Example 7 is the computing system of any or all previous examples andfurther comprising:

activity log page generator logic that receives the invocation signalfrom the activity log invocation logic and generates an activity logdisplay showing log entries in the activity log generated based ondetected user activity of the user.

Example 8 is the computing system of any or all previous exampleswherein the activity log page generator logic generates the activity logdisplay with log entries that were generated across a plurality ofdifferent browser sessions of the web browser.

Example 9 is the computing system of any or all previous exampleswherein the activity log page generator logic generates the activity logdisplay with N most recent log entries arranged on the activity logdisplay in order of recency.

Example 10 is the computing system of any or all previous exampleswherein the UI element comprises an undo actuator and furthercomprising:

interaction processing logic configured to control the email system toundo the activity taken relative to the corresponding email message inresponse to user actuation of the undo actuator.

Example 11 is the computing system of any or all previous exampleswherein the UI element comprises a retrieval actuator and furthercomprising:

interaction processing logic configured to control the email system toretrieve and surface full email content for email message identified inthe log entry.

Example 12 is a computer-implemented method, comprising:

exposing, user accessible electronic mail (email) functionality toperform a plurality of different types of activities relative to anemail message;

generating an activity log that has log entries, each log entryidentifying an activity taken relative to a corresponding email messageand identifying the corresponding email message, the activity log havinga log entry generated in the activity log for each of the plurality ofdifferent types of activities taken relative to different correspondingemail messages, at least one log entry including a user interfaceelement that is user actuatable to perform an action relative to the logentry; and

generating a control signal to control surfacing of the activity log.Example 13 is the computer-implemented method of any or all previousexamples exposing comprises exposing the user accessible emailfunctionality through a web browser and wherein generating the activitylog comprises:

identifying a detected user activity taken relative to a givencorresponding email message; and

identifying the given corresponding email message.

Example 14 is the computer-implemented method of any or all previousexamples wherein generating the activity log comprises:

generating a corresponding activity log entry, in the activity log, thatidentifies the detected user activity performed relative to the givencorresponding email message, and further comprising exposing theactivity log through the web browser.

Example 15 is the computer-implemented method of any or all previousexamples and further comprising:

detecting user invocation of the activity log, corresponding to theuser, through the web browser;

generating an invocation signal indicative of the detected userinvocation; and

generating an activity log display showing log entries in the activitylog generated based on detected user activity of the user.

Example 16 is the computer-implemented method of any or all previousexamples wherein generating the activity log display comprises:

generating the activity log display with log entries that were generatedacross a plurality of different browser sessions of the web browser.

Example 17 is the computer-implemented method of any or all previousexamples wherein the UI element comprises an undo actuator and furthercomprising:

controlling the email functionality to undo the activity taken relativeto the corresponding email message in response to user actuation of theundo actuator.

Example 18 is the computer-implemented method of any or all previousexamples wherein the UI element comprises a retrieval actuator andfurther comprising:

controlling the email functionality to retrieve and surface full emailcontent for email message identified in the log entry.

Example 19 is a computing system, comprising:

a web-based electronic mail (email) system that is user accessiblethrough a web browser to perform a plurality of different types ofactivities relative to an email message;

activity identifier logic that identifies any detected user activity, ofa plurality of different types of user activity, taken relative to agiven corresponding email message;

item identifier logic that identifies the given corresponding emailmessage;

logging logic that generates a corresponding activity log entry, in anactivity log, that identifies the detected user activity performedrelative to the given corresponding email message, the log entryincluding a user interface element that is user actuatable to perform anaction relative to the log entry, the web-based email system beingconfigured to expose the activity log through the web browser; and

interaction processing logic configured to control the email system toundo the activity taken relative to the corresponding email message inresponse to user actuation of the user interface element.

Example 20 is the computing system of any or all previous examples andfurther comprising:

activity log page generator logic configured to receive an invocationsignal from activity log invocation logic and generate an activity logdisplay showing log entries in the activity log generated across aplurality of different browser sessions of the web browser based ondetected user activity of the user.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

What is claimed is:
 1. A computing system comprising: at least one processor; and memory storing instructions executable by the at least one processor, wherein the instructions, when executed, cause the computing system to: generate an activity log comprising activity log entries representing a plurality of different types of activities performed by an electronic mail (email) system relative to email messages, wherein each activity log entry comprises: an activity identifier that identifies an activity performed relative to a corresponding one of the email messages, that corresponds to the activity log entry; and a message identifier that identifies the corresponding email message; and generate a user interface that includes a user interface element representing at least one of the activity log entries in the activity log, the user interface element including an indication of the corresponding activity and message identifiers, that correspond to the at least one activity log entry, wherein the user interface element is actuatable to perform an action relative to the at least one activity log entry.
 2. The computing system of claim 1, wherein the email system is a web-based email system that is user-accessible through a web browser and wherein, the instructions cause the computing system to: identify a particular one of the activities taken relative to a particular one of the email messages and to generate the activity identifier that identifies the particular activity.
 3. The computing system of claim 2, wherein the instructions cause the computing system to: identify the particular email message and generate the message identifier that identifies the particular email message.
 4. The computing system claim 3, wherein the instructions cause the computing system to: generate a corresponding activity log entry, in the activity log, that identities the particular: activity performed relative to the particular email message, the web-based email system being configured to expose the user interface through the web browser.
 5. The computing system of claim 4, wherein the instructions cause the computing system to: detect user actuation of an activity log display element, that represents the activity log on the user interface display; and based on the detected user actuation of the activity log display element, display the user interface element representing the at least one activity log entry.
 6. The computing system of claim 5, wherein the instructions cause the computing system to: based on the detected user actuation of the activity log display element, generate an activity log display showing log entries in the activity log generated based on detected user activity corresponding to the user.
 7. The computing system of claim 2, wherein the instructions cause the computing system to generate the activity log with activity log entries that were generated across a plurality of different browser sessions of the web browser.
 8. The computing system of claim 7, wherein the instructions cause the computing system to generate the user interface with a set of user interface elements that represent the N most recent activity log entries arranged in order of recency.
 9. The computing system of claim 1, wherein the user interface element comprises an undo actuator, and the instructions cause the computing system to: in response to user actuation of the undo actuator, control the email system to undo the activity taken relative to the corresponding email message, that corresponds to the at least one activity log entry.
 10. The computing system of claim 1, wherein the user interface element comprises a retrieval actuator, and the instructions cause the computing system to: control the email system to retrieve and surface full email content for the corresponding email message, that corresponds to the at least one activity log entry.
 11. A method performed by a computing system, the method comprising: generating an activity log comprising activity log entries representing a plurality of different types of activities performed by an electronic mail (email) system relative to email messages, wherein each activity log entry comprises: an activity identifier that identifies an activity performed relative to a corresponding one of the email messages, that corresponds to the activity log entry; and a message identifier that identifies the corresponding email message; and generating a user interface that includes a user interface element representing at least one of the activity log entries in the activity log, the user interface element including an indication of the corresponding activity and message identifiers, that correspond to the at least one activity log entry, Wherein the user interface element is actuatable to perform an action relative to the at least one activity log entry.
 12. The method of claim 11, wherein the email system comprises a web-based email system that is user accessible through a web browser, and wherein generating the activity log comprises: identifying a detected user activity taken relative to a particular one of the email messages.
 13. The method of claim 12, wherein generating the activity log comprises: generating a corresponding activity log entry, in the activity log, that identifies the detected user activity performed relative to the particular email message, and further comprising exposing the user interface through the web browser.
 14. The method of claim 13, and further comprising: detecting user actuation of an activity log display element, that represents the activity log on the user interface display; and based on the detected user actuation of the activity log display element, displaying the user interface element representing the at least one activity log entry.
 15. The method of claim 12, wherein generating the activity log comprises: generating the activity log with activity log entries that were generated across a plurality of different browser sessions of the web browser.
 16. The method of claim 11, wherein the uses interface element comprises an undo actuator and further comprising: controlling the email functionality to undo the activity taken relative to the corresponding email message in response to user actuation of the undo actuator.
 17. The method of claim 11, wherein the user interface element comprises a retrieval actuator and further comprising: controlling the email functionality to retrieve and surface full email content for email message identified in the activity log entry.
 18. A computing system comprising: at least one processor; and memory storing instructions executable by the at least one processor, wherein the instructions, when executed, provide: an activity log generator configured to: generate an activity log comprising activity log entries representing a plurality of different types of activities performed by, an electronic mail (email) system relative to email messages, wherein each activity log entry comprises: an activity identifier that identifies an activity performed relative to a corresponding one of the email messages, that corresponds to the activity log entry; and a message identifier that identifies the corresponding email message; and a user interface component configured to: generate a user interface that includes a user interface element representing at least one of the activity log entries in the activity log, the user interface element including an indication of the corresponding activity and, message identifiers, that correspond to the at least one activity log entry, wherein the user interface element is actuatable to perform an action relative to the at least one activity log entry.
 19. The computing system of claim 18, wherein the email system is a web-based email system that is user-accessible through a web browser and wherein the activity log generator is configured to: identify a particular one of the activities taken relative to a particular one of the email messages and to generate the activity identifier that identifies the particular activity.
 20. The computing system of claim 19, wherein the activity log generator is configured to: identify the particular email message and generate the message identifier that identifies the particular email message. 